-
Notifications
You must be signed in to change notification settings - Fork 38.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
move well known cloud provider taints to k8s.io/cloud-provider/api #88435
Conversation
8571c6c
to
5e932c0
Compare
5e932c0
to
1bcb92b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM from sig-node perspective. I don't think we have any opinions around whether we import these values from pkg/scheduler
or pkg/cloud-provider
. It looks like we already depend on both :)
/retest |
Vendor Verify failed. |
Signed-off-by: andrewsykim <kim.andrewsy@gmail.com>
1bcb92b
to
8c63335
Compare
/retest |
/approve for the scheduler changes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
ref #81172 |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ahg-g, andrewsykim, liggitt The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Signed-off-by: andrewsykim kiman@vmware.com
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Moves well known cloud provider taints from
pkg/scheduler/api
tok8s.io/cloud-provider/api
. This is part of an effort to remove internal deps in all cloud controllers so they can be moved to a staging repo.Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: